home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Chip 2005 August
/
CHIP_CD_2005-08.iso
/
bonus
/
photo_rest
/
files
/
setup.exe
/
{app}
/
DOS
/
LNG
/
english.lng
< prev
Wrap
Text File
|
2002-07-02
|
19KB
|
496 lines
║ For FAT16/FAT32 filesystems. ║|
║ Not for commercial use. ║|
Please press Ctrl+Break now if you haven't read the manual completely|
Unable to continue previous analysis - file load failed or cancelled.|
Select physical disk to recover data from (F1=Help)|
║ ID ║ Cylinders ║ Heads ║ Sectors ║ Total Sectors ║ Size, MB ║ Access ║|
║ Use disk image in file ║|
║ Previous scan results will be loaded. Please select a disk now. ║|
║ Load previous scan results ║|
There are no compatible disks attached|
Enter image file name : |
WARNING : |
Image file size is not an even multiple of sector size|
Image file accepted: |
sector(s)|
Testing...|
ERROR! |
║ Recalibrate drive ║ ║|
║ Legacy controller RAM diagnostics ║ ║|
║ Legacy drive diagnostics ║ ║|
║ Controller self-test ║ ║|
Skipped |
Checking Int 13h extensions support : |
Not detected|
Checking DPMI support : |
DPMI ERROR: Unable to allocate DOS memory block (memory low?)|
DPMI ERROR: Real mode interrupt call failed|
Press any key|
Partition table sector | Linked with next!
read failed|
Partition table sector | Linked with next!
signature is bad|
Partition table on the disk seem to be damaged.|
║ I want to enter volume start offset and size in megabytes ║|
║ I want to enter volume start offset and size in sectors ║|
║ There was only one volume on disk, so I want to scan the entire disk ║|
Select partition to recover, or enter parameters manually (F1 = Help)|
║Type║ OS / Filesystem type ║Active║Start at, Mb║Vol. size, Mb║Boot Sig║|
Yes|
No |
Volume start offset is usually a sum of sizes of all volumes before this|
Enter volume start offset (in megabytes) : |
Enter volume size (in megabytes) : |
Enter volume start offset (1st phys sector number) : |
Enter volume size (in sectors, 2048 sectors per Mb): |
Invalid search area selected, start of area is beyond the end of disk|
Invalid search area selected, end of area is beyond the end of disk|
You specified : |
End of disk : |
Do you want to set end of area to last sector on disk and proceed? [Y/N/F1] :|
Zero Assumption Recovery version 7.1.0|
║ Registration information is available at ║|
http://www.z-a-recovery.com/ |
Mem: |
-- Last error: |
Read operation on directory sector | Linked with next!
failed|
Total | Linked with next!
file entries added after directory scan|
Number of sectors per cluster must be a power of two: 1, 2, 4, 8, ..., 512|
CF (number of sectors per cluster) guessing started...|
Testing of CF = | Linked with next!
resulted in | Linked with next!
% errors|
Based on the above, CF (number of sectors per cluster) determined to be |
If you know this is incorrect, you can specify CF manually by pressing "N" now|
Do you want to accept the autodetected value? [Y/N/F1] : |
Please enter a range of possible CF (number of sectors per cluster) values|
Minimum number of sectors per cluster: |
Maximum number of sectors per cluster: |
Range from |
to |
is not correct.|
CF/SS determination started. This may take a long time, please wait...|
║ Sectors Per Cluster (CF)║ Start Sector (SS) ║ Relevance ║|
║ I want to enter parameters manually (F1=Help) ║|
CF (Sectors per cluster): |
SS (Start sector) : |
WARNING: Character set file not found, default (English) will be used|
ERROR (Start=| Linked with others!
) - Unexpected free cluster|
) - Circular reference|
) - Chain too short|
) - Chain too long|
Adding FAT entry: cluster |
║If you know what filesystem was this volume using, please specify it (F1=Help)║|
║ I know that filesystem on volume was FAT16 ║|
║ I know that filesystem on volume was FAT32 ║|
║ Autodetect filesystem type ║|
Searching for FATs, reading sector |
Detecting FAT16 - Computing FAT size statistics|
Detecting FAT32 - Computing FAT size statistics|
Detecting FAT16 - Computing FAT start sector statistics|
Detecting FAT32 - Computing FAT start sector statistics|
Sorting...|
Best relevance is |
FAT search completed|
║ No ║ StartSec/Size ║ Type ║Volume size, Mb ║Signature║ Boot ║ M.F./Rel. ║|
║ None of that applies, I want to enter parameters manually ║|
║ None of that applies, I want to proceed assuming all FAT entries junk ║|
Enter FAT start sector number (1st FAT): |
Enter FAT size in sectors : |
Select FAT type: 1 = FAT16, 2 = FAT32 : |
Please enter approximate volume size in megabytes: |
Identification failed. This volume is probably damaged beyond repair.|
Scan: |
sector(s) identified. |
left| Time in scan
║ File type ║ Use this type ║|
║ Yes (required) ║|
Yes ║|
No ║|
║ Proceed ║|
Recover long file names (LFNs)|
Recover erased files|
LFN filtering mode|
Allow N invalid symbols in names|
Skip files > X Mb, 0 - no skips |
Simulation mode (DEBUG)|
Strict|
Loose|
Please set configuration options. Leave defaults when not sure (F1 = Help).|
║ Option name ║ Value ║|
New value for | Linked with next!
. Must be from | Linked with next!
to |
LFN updated for directory: |
, cluster |
Directory rename skipped: | Linked with next!
to |
Entry updated: |
Fragment added: |
(Sub)directory added: |
File named "| Linked with next!
skipped (bad name, | Linked with next!
bad char(s))|
Directory name "| Linked with next!
was discarded (|
Directory sector read failed |
Sector read failed | Linked with next!
), directory at | Linked with next!
will be orphan|
Directory "| Linked with next!
) was linked to parent "|
Cluster is valid by | Linked with next!
sector (LAST or SHORT)|
Fragment processing started : |
(Sub)directory processing started : |
Fragment processing done |
FAT entry for directory | Linked with next!
is corrupt|
processing done | (FAT) processing done - Linked with next!
cluster(s)|
Refining directory tree, pass |
*** Directory tree was refined with |
passes ***|
Final pass: looking up names, parsing files...|
Directory at cluster | Linked with next!
was named |
Enter file name to write to, or press Enter to cancel :|
File already exists, overwrite? [Y/N]:|
File creation error!|
Scan save file will be loaded now.|
Enter file name, or press Enter to cancel:|
Error - Cannot open file|
Operation failed - file error encountered|
Writing file header... |
Done. |
Writing data... |
record(s) saved.|
Error : file format is invalid|
Reading header... |
bad signature|
unsupported file format version|
Disk size mismatch, need | Linked with next!
, got |
May be a wrong savefile, continue anyway? [Y/N/F1]:|
Reading data... |
record(s) loaded.|
Do you want to save scan results to file? [Y/N]:|
Fatal error : Out of memory. Program will now exit. |
Ignore case in long file names|
Building preliminary file list, |
Guessing CF (Number of sectors per cluster)|
Detecting SS, CF=| Linked with next!
tested (| Linked with next!
, Best = |
CF/SS detection done|
Scanning disk and identifying data|
Determining volume parameters|
Searching for FATs|
Reconstructing directory tree|
Please select intefrace mode now (F1 = Help)|
║ Simple mode (all decisions are made automatically, no questions asked) ║|
║ Advanced mode (you will be asked to confirm ZAR decisions and set options) ║|
An error has occured and ZAR is unable to continue execution in simple mode |
ZAR is currently scanning the selected area of the disk|
searching for data that can be identified (such as directories).|
These records will be used later during analysis.|
ZAR is determining volume layout now.|
During this stage, CPU-intensive statistical|
algorithms are used, so it can take a long time.|
ZAR is currently searching for File Allocation Tables on disk.|
FATs are of great significance when it comes to data recovery.|
However, the recovery will still be attempted if FATs are damaged.|
This is a final stage of the analysis. ZAR is currently processing|
all directories previously found. File names and locations, as well|
as a directory tree structure information is being collected.|
-Move; |
Space|
-Tag/Untag; |
-Start; |
All; | +All, -All
Invert; |
asks | - from Masks
Select directories to recover. | Linked with next
Mb selected|
Ready|
Space required - |
Free on drive | Linked with next: FREE ON DRIVE X: -
: - |
- low space?|
Select destination directory to copy recovered files to|
or press <Enter> to accept default directory|
Directory does not exist - |
Creation failed|
Created OK|
ERROR: Cannot create LFN information file, |
║ File copy progress : |
of |
files done ║|
║ Current file name : |
║ Current method : |
║ Current file size : |
Copying files, ESC - skip current file...|
Cannot write file, disk full?|
Skipped|
DIRECT|
FAT (both)|
FAT (1st)|
FAT (2nd)|
║ Recovery statistics ║|
║ Total files : |
║ Both FATs were valid : |
║ Only 1st FAT was valid : |
║ Only 2nd FAT was valid : |
║ Both FATs were bad : |
single cluster files) ║|
Select file masks. Note: these masks will be applied to 8.3 names only|
║ Include ║ Exclude ║|
Arrows|
- Move; |
Enter|
- Edit; |
- Accept and exit|
ZAR is currently analysing the disk.|
There is an activity indicator in a top left corner of the screen.|
Some information about the processing is also displayed in the status bar.|
Skip files when both FATs are bad|
║ For partition/boot sector analysis ║|
║ Now scanning sector |
% completed ║|
║ Last object found : |
, in sector |
Error creating or writing file |
Scan mode |
Fast |
Full |
Save copies of sectors |
Sector |
contains a FAT16 boot sector|
Volume label : |
OEM ID : |
Sectors per cluster : |
Reserved sector(s) : |
Sector(s) per FAT : |
Root directory entries : |
Total sectors on disk : |
contains a FAT32 boot sector|
Approx. volume size, Mb : |
ZAR: Disk area - start sector : |
ZAR: Disk area - size in sectors : |
ZAR: CF/SS pair : |
ZAR: FAT start sector : |
ZAR: FAT size in sectors : |
seems to contain |
an Extended Partition Pointer|
a Master Boot Record|
WARNING: loader code seems to be incorrect or missing|
Partition layout as recorded in sector :|
Filesystem type|
Start End Rel Start Abs Size|
Cyl Head Sec Cyl Head Sec|
Information computed from the above data|
Abs start Abs size Approximate volume size, Mb|
The partition table seems to be incorrect and/or untrustworthy.|
The following inconsistinties were found:|
Significant amount of a disk space is unallocated|
Total volume size exceeds physical disk capacity|
Some volumes overlap|
Bogus information is recorded for some volume(s)|
Invalid volumes encountered and they were discarded|
F1 = Help|
Skip duplicate files| from OptionCf
No help file was found for the selected language!|
ERROR : |
ERROR : The help file cannot be found or read from|
Press ESC to return back to program|
ERROR: The help topic you requested cannot be found|
Topic ID is |
A help file is probably damaged. If you are sure it is OK, please report a bug|
ZAR Help window. Press ESC to close help and return to program.|
Duplicate file check disabled (low memory).|
CF/SS search complete|
Choose volume parameters determination algorithm (F1 - Help)|
║ Complete dataset brute-force (very slow, use for mirrored volumes only) ║|
║ Reduced dataset brute-force (recommended) ║|
║ Parameters will be specified manually (not recommended) ║|
should contain a boot record, but nothing was found|
Windows SUHDLOG.DAT information found near sector |
recorded in SUHDLOG.DAT matches the sector on disk|
found in SUHDLOG.DAT. Sector on disk does not match the one in file.|
Dump of the expected sector contents follows : |
Unable to interpret sector.|
End of the expected sector contents dump|
Enter file name to save report to, or press Enter to accept |
default path and file name |
There is an error in a drive geometry info reported by BIOS.|
It is reported to be of 0 tracks, cylinders or sectors.|
Enter a Sectors Per Track value (enter 1 if not sure): |
MBR or EPP|
FAT16 boot sector|
FAT32 boot sector|
Win9x SUHDLOG.DAT|
Collecting final data, please wait...|
ERROR|
No compatible floppy drives found|
Select a floppy disk to write to|
║ Cancel ║|
Cancelled by user|
There is no disk in drive, or the disk is not formatted.|
The disk is write protected.|
The disk is must be empty.|
Select a tool to write|
Loading module file |
File not found : |
File appears to be damaged : |
Disk read error|
Disk write error|
Reading boot loader file, |
Adjusting boot sector... |
Disk Eraser (writes zeros to disk)|
Disk Copier (sector-by-sector copy)|
MBR Eraser (writes zeros to MBR)|
Do you want to retry? [Y/N/F1] : |
Writing module sectors... |
║ LIMITED EVALUATION VERSION ║|
║ REGISTERED VERSION ║|
FAT search complete. Select parameters from list now (F1 = Help)|
║ Boot-Based Tools ║|
║ For NTFS filesystem [Beta version] ║|
MFT fragments(s) found on disk.|
Table of MFT regions overflowed, please report a bug!|
Preparing data for MFT region assignment |
% complete|
Performing MFT region assignment |
Performing region validation |
Too many MFT entries unassigned|
Scanning MFT (2nd pass) |
Scanning MFT (1st pass) |
║ Sectors per FRS ║ Bytes per FRS ║ Relevance ║|
║ Sectors Per Cluster ║ Starting sector ║ Relevance ║|
║ I want to enter parameters manually (F1-Help) ║|
CF must be 1, 2, 4, 8, or 16|
Determining volume parameters|
Reading directory tree (preliminary) |
Reading directory tree (final) |
Building directory structure in memory...|
Reviewing unlinked entries...|
║ Current file name ║ |
║ Current file size ║ |
║ Special notes ║ |
[Resident] |
[Nonresident] |
INTERNAL: Invalid filesystem type, please report a bug!|
Filesystem-specific data buffer size mismatch|
Select FRS size to use (F1 - Help)|
Select CF/SS pair to use (F1 - Help)|
[Compressed] |
[Sparse] |
Scanning disk and identifying data|
Analysing volume Master File Table|
Determining volume parameters|
Reconstructing directory tree|
ZAR is currently scanning the selected area of the disk|
searching for data that can be identified.|
These records will be used later during analysis.|
ZAR is analysing Master File Table on volume.|
Filesystem structures are being parsed and sorted.|
|
ZAR is currently determining volume parameters|
required to locate files on volume|
|
This is a final stage of the analysis. ZAR is currently processing|
all directories previously found. File names and locations, as well|
as a directory tree structure information is being collected.|
Checking dataset size |
OK|
Too much data|
Trimming dataset...|
Unable to reduce dataset any further|
Removing |
record(s)|
Final dataset size |
Preliminary file list trimmed down to |
NTFS boot sector|
contains an NTFS boot sector|
Clusters per FRS : |
Clusters per INDX block: |
Unsupported volume size|
Bytes per FRS : |
ATTENTION!|
Unexpected error encountered while committing changes.|
Current state of the disk may be inconsistent.|
WARNING!|
An unexpected condition has been detected.|
No changes were made to the disk.|
Assertion fault, config line |
Action was : |
Reason was : |
ROW missing in configuration file, line |
Invalid ROW in configuration file, line |
is invalid in configuration file, line |
Enter configuration file name : |
Unable to open configuration file.|
Phase 1 - checking assertions (if any)...|
Error in configuration file, line |
Generic|
Checking |
boot signature|
55AA check|
Data mismatch|
partition row |
Partition row check|
mismatch|
Assertion tests completed successfully|
Phase 2 - committing changes (if any)...|
Adjusting |
Already OK - |
Disk modification completed successfully|
Parameter(s) loaded from configuration file|
Configuration file : |
Loaded|
Not used|
Error parsing configuration file|
detected while reading|
in line|
Default value will be used if possible, press any key..|
Invalid syntax|
Error in FROM|
Error in TO|
Invalid numeric format|
ERROR: Cannot open configuration file |
Invalid option value|
Simple mode will be used|
Advanced mode will be used|
Image name|
Going to analyze physical disk|
Invalid disk specified|
Image file write error|
Scan area definition|
Invalid range|
Using CF = |
Unable to autodetect disk parameters|
Sorting...|
Discarding FATs|
Explicit FAT parameters loaded|
Invalid option combination|
Scroll up to see more...|
Scroll down to see more...|
Starting copy|
Default file type settings will be used to scan|
All known file types will be used to scan|
Only required file types will be used to scan|
Using| this and next one form the following: "USING [value] FOR [option]"
for|
Coalesce directory fragments|
Enter CF (Sectors Per Cluster) : |
Enter SS (Start Sector) : |
Too many nested directories!|
Using FRSSize = |
Using SS = |
Failed to assign | !Linked with next
% of MFT entries|
║ Boot record editor ║|
file(s)